Skip to content

replace "value" with "contents" for Aeson compatibility #116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

peterbecich
Copy link

@peterbecich peterbecich commented Nov 26, 2023

Description of the change

Suggestion: #115

Feedback appreciated


Checklist:

  • Added the change to the changelog's "Unreleased" section with a link to this PR and your username
  • Linked any existing issues or proposals that this pull request should close
  • Updated or added relevant documentation in the README and/or documentation directory
  • Added a test for the contribution (if applicable)

@garyb
Copy link
Member

garyb commented Nov 26, 2023

I would imagine this won't be accepted because it's a massively breaking change for people who are currently using the library.

One possible option would be to change it to always write contents but try and read from contents and value so that it's backwards compatible for decoding at least, but it'd still consider that to be breaking.

@peterbecich
Copy link
Author

Great points, thanks.

What if it were configurable somehow, and the default remains "value"?

@peterbecich
Copy link
Author

more discussion here #115 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants